feat(op): pull chain config from superchain-registry github #19914
Conversation
0xPenryn
requested review from
Rjected,
fgimenez,
gakonst and
mattsse
as code owners
|
is it really needed to wait for new release to pull the latest registry now? isn't it just a matter of replacing the json file on the specific path manually? agree though that it's cooler if this is done automatically. |
Locally updating the files generated from the Superchain Registry is possible if you're building Most World Chain node operators use Docker images to run their nodes, and requiring them to pull an updated genesis file and pass that into the Docker image is exactly the friction that the Superchain Registry integration is designed to prevent. I'm simply trying to reduce that friction even further, and also remove the need for chain operators like us to ask for new releases just so the Before this PR:
After this PR:
|
2 participants
Updates the
reth-optimism-chainspeccrate, adding functionality to pull the latest chain configuration directly from the superchain registry. If the superchain registry is unreachable, it will fall back to the local chain configurations and follow the existing behavior.This means that op-reth doesn't need to cut a new release to reflect updates to the superchain registry; rather, the node operator simply needs to restart op-reth and it will pull the latest config.